Search Result

I am implementing nrfx uarte on nRF52840 with ncs 2.6.1. I am using the example provided in modules\hal\nordic\nrfx\samples\src\nrfx_uarte as a reference. Reason for using nrfx instead of zephyr API is the ability to change UART TX and RX pins during runtime. Because my design contains 3 UART devices. I am sure that there is only one line calling IRQ_CONNECT and I have tried clean build configuration and rebuild but the problem persist. If I comment out IRQ_CONNECT function, the code build without error but nothing is shown in the console log if I run the code. I have found only 1 similar thread said that config CONFIG_NRFX_I2S0=y and CONFIG_I2S_NRFX=n to avoid this problem( IRQ_CONNECT duplication causing gen_isr_tables.py to fail ). But CONFIG_UARTE1_NRFX does not exist. main.c #include #include #include LOG_MODULE_REGISTER(nrfx_sample, LOG_LEVEL_INF); #define UARTE_INST_IDX 1 #define UARTE_TX_PIN 31 #define UARTE_RX_PIN 30 static uint8_t m_tx_buffer[] = {0x01, 0x03, 0x01, 0x00, 0x00, 0x01,

Hi, I am using NCS v2.4.2 and nRF5340DK + nRF21540EK but I can not enable GPIO+SPI mode. for example, I use nrf/samples/bluetooth/central_and_peripheral_hr application. I built the following. west build -p -b nrf5340dk_nrf5340_cpuapp -d build-ble-hrs nrf/samples/bluetooth/central_and_peripheral_hr -- \ -DSHIELD=nrf21540_ek_fwd -Dhci_rpmsg_SHIELD=nrf21540_ek I checked netcpu config but GPIO+SPI mode was not enabled. I did not modify NCS code. what should I do? also, I tried to add child/hci_rpmsg.conf and add the folloing in the conf file. CONFIG_MPSL_FEM_NRF21540_GPIO_SPI=y I could enable GPIO+SPI mode by the conf file but the following error output. It seems netcpu side is crushed. Please help me.

We are working on a custom board (gateway BIS) with the nrf5340. Currently our system is on the 2.5.2 SDK and we currently have FOTA working with an external QSPI flash and updating both the app partition and the BLE core partition simultaneously. We are currently porting this code to the latest 2.6.0 SDK as we would like to take advantage of the SoftDevice controller and some of the features it offers (Channel Mapping). I have converted the example code changes from the nrf5340_audio example (as this was the basis for our project.) When I try to build with the buildprog.py script this is the error I now get. python buildprog.py -c both -b debug -d gateway -m external -M --pristine -p Traceback (most recent call last): File "buildprog.py", line 501, in __main() File "buildprog.py", line 387, in __main raise Exception("DFU arguments only accepted when using controller: " + Exception:

Hello, could someone point me where I can find the most current / state of the art example for the BLE UART app for the nRF25840 Dongle? The version in the nRF5_SDK does not support the dongle. I guess the latest examples work with VS Code rather than Segger. Unfortunately I have not found anything so far. What I want to achieve: Quickly have an working example on my dongle that transmits incoming strings from BLE to serial and vice versa. Many thanks in advance. Regards, Andreas

Hi, I am adapting the Azure IoT example for use with the nRF5340DK and nRF7002EK. The configuration is: - sdk: nvs 2.6.0 - example Azure IoT hub Initially, the getaddrinfo() function returns a failure code of -101 when called in the broker_init. After that, I implemented the DNS resolver, dns_resolve_init(), which changed the return error to -11. Could you please assist me in resolving this issue? prj.conf CONFIG_NET_IPV6=n CONFIG_NET_IPV4=y CONFIG_NET_DHCPV4=n # Enable Sockets support CONFIG_NET_SOCKETS=y CONFIG_NET_SOCKETS_SOCKOPT_TLS=y # Enable the DNS resolver CONFIG_DNS_RESOLVER=y # Enable additional buffers CONFIG_DNS_RESOLVER_ADDITIONAL_BUF_CTR=5 # Enable additional queries CONFIG_DNS_RESOLVER_ADDITIONAL_QUERIES=2 # Enable mDNS support CONFIG_MDNS_RESOLVER=y # Enable LLMNR support CONFIG_LLMNR_RESOLVER=n CONFIG_DNS_RESOLVER_MAX_SERVERS=1 CONFIG_DNS_SERVER_IP_ADDRESSES=y CONFIG_DNS_NUM_CONCUR_QUERIES=5 CONFIG_DNS_RESOLVER_LOG_LEVEL_DBG=y # Google DNS IPv4 and IPv6 servers CONFIG_DNS_SERVER1="8.8.8.8" # CONFIG_DNS_SERVER2="2001:4860:4860::8888" CONFIG_NET_CONFIG_SETTINGS=y CONFIG_NET_CONFIG_NEED_IPV6=n CONFIG_NET_CONFIG_NEED_IPV4=y CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.0.2.1" CONFIG_NET_CONFIG_PEER_IPV4_ADDR="192.0.2.2" Terminal *** Booting nRF Connect SDK v3.5.99-ncs1 *** [00:00:00.014,862] wifi_nrf_bus: SPIM spi@a000: freq = 8 MHz [00:00:00.014,923] wifi_nrf_bus: SPIM spi@a000: latency = 0 *** Booting nRF Connect SDK v3.5.99-ncs1

Hi, We've got a board with a fairly limited power supply in production and it's expected to brown out under certain conditions. As such, I need to verify the reset loop prevention described in this Nordic Semiconductor white paper. I'm using mfw_nrf9160_1.3.5 and SDK 2.0, so I expect the prevention to trigger after 7 resets. To test this I unconditionally trigger a connection during the boot sequence and have our power supply limited to ~30 mA to trigger a brown out. I can see +CEREG: 2 and +CSCON: 1 just before each reset, so the device appears to be browning out during active comms, but it never triggers the reset loop prevention. I let it reset approx 20 times before stopping the test. I never call +CFUN=0 and can't it doesn't appear to be called from any sdk code as if I breakpoint in `lte_lc_func_mode_set` it never triggers. Any help

Hi all. I have made myself a board which has a module with the nRF52833 chip embedded onto it. It's effectively a board with a set of switching regulators on it to drive multiple strings of LEDs. I have been testing the board with relatively small strings of SK6812 RGBW LEDs - up to 120 or so - and all has been working fine. Today I have received a longer strip of LEDs and I'm apparently having issues driving it. The code is relatively simple, I am generating pixels and sending them towards the strip using the ws2812_spi driver: ret = led_strip_update_rgb ( strips [ i ]-> device , strips [ i ]-> buffer , offset ); // Update physical An example of my config (there's one for each of the four SPI buses): & spi2 { compatible = "nordic,nrf-spim" ; status = "okay" ; pinctrl-0 = ; pinctrl-1 =

I use one channel of the SAADC on nRF52832 to measure the power supply voltage. Code for configuration & operation of SAADC attached: #include "adc.h" #include "main_keyboard.h" #include "nrf_drv_saadc.h" #include "nrf_log.h" #include "app_scheduler.h" /** * Adapted from: https://github.com/NordicPlayground/nRF52-ADC-examples/tree/master/saadc_low_power */ #define SAADC_SAMPLES_IN_BUFFER 1 // Number of SAADC samples in RAM before returning a SAADC event. For low power SAADC set this constant to 1. Otherwise the EasyDMA will be enabled for an extended // time which consumes high current. #define SAADC_OVERSAMPLE NRF_SAADC_OVERSAMPLE_4X // Oversampling setting for the SAADC. Setting oversample to 4x This will make the SAADC output a single averaged value when the SAMPLE task is triggered 4 times. // Enable BURST mode to make the SAADC sample 4 times when triggering SAMPLE task once. #define SAADC_BURST_MODE 1 // Set to 1 to enable BURST mode, otherwise set to 0. static nrf_saadc_value_t buffer[SAADC_SAMPLES_IN_BUFFER]; static void saadc_isr_callback(nrf_drv_saadc_evt_t const *p_event); static void

Hi all, Could anyone share a code example for sending sensor data over BLE using the NUS Service in Zephyr RTOS? I'm new to this field and struggling to get data from the MAX30102 sensor over BLE. If you could provide any samples, I would greatly appreciate it. Thank you, Fernando

Hi , Our custom board uses the nRF52840 chip, and we followed the Nordic official webinar 'Adding Custom Board Support in nRF Connect SDK' during development. We noticed that the blinky sample example does not work in debug mode or after flashing. In debug mode, the code halts somewhere in reset.s or sometimes the cpu_idle file, but it never reaches the main function. After significant troubleshooting, we discovered that the LED blinks and single stepping becomes possible if we enable the internal RC oscillator with the following configurations in the prj.conf file: #Internal RC low-frequency oscillator (LFRC) CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y We're also working with the hardware team to investigate potential issues with the external crystal or capacitors. We'd like to investigate the issue from a firmware perspective simultaneously. The same problem has been observed on three separate boards. Thanks & Regards, Gaurav